Prioritization of protocol messages at a server

ABSTRACT

System(s) and method(s) are provided for prioritizing protocol messages received at a server. A client generates a request message and incorporates a data unit therein in order to indicate type of service application that triggered generation of the request message. The client conveys the request message to a server configured to respond to the request message. To supply data in response to the message request, the server prioritizes the request message based at least on the data unit that conveys the type of service application. The server can assign a set of request messages to a group of scheduling queues based at least on ranking of the type of service associated with at least one request message in the set of request messages. Based on performance conditions, the server also can reject one or more request messages according to the ranking.

TECHNICAL FIELD

The subject disclosure relates generally to communication networks and,more specifically, to prioritization of protocol messages received at aserver, wherein the prioritization is based at least on feature(s) of aservice client, such as application client or a control client, thatoriginates the protocol messages.

BACKGROUND

Various services in advanced networks, wireless or wireline, rely onpacket-based protocols for delivery of data and signaling. Such advancednetworks generally exploit a group of application servers that generateat least part of the data and signaling that provide content and enablespecific functionality associated with a service, such as voice overinternet-protocol (VoIP), IP multimedia content delivery, calleridentification (ID) in IP television, etc. In certain architectures, thegroup of servers is deployed in an application layer, which isfunctionally coupled to a control layer that typically includes severalsession control components that enable a service session (e.g., a VoIPcall, a data call, delivery of a pay-per-view movie . . . ). An exampleof such architecture is 3GPP IP Multimedia System (IMS) core network. In3GPP IMS core network, a session control component is embodied in acontrol session control function (CSCF) node, which can be a ServingCSCF (S-CSCF) node, Interrogating CSCF (I-CSCF) node, a Proxy-CSCF(P-CSCF) or a transit function node. In addition, in 3GPP Long TermEvolution (LTE) networks, a Mobility Management Entity (MME) can embodya session control component.

To enable, in part, access of a subscriber device (mobile device,customer premises equipment, etc.) to network resources associated witha service, application servers, session control components, or othernetwork nodes, generally acquire data from a centralized networkrepository, which operates as a master database. In 3GPP architecturefor next generation networks (NGN), Home Subscriber Server (HSS) canembody the centralized network repository master user database. A HSScan contain subscription-related information (subscriber profiles,subscriber credentials, etc.). In addition, the HSS can performauthentication and authorization of a subscriber device, and can provideinformation about the subscriber's location and IP information. HSS alsocan provide services to call processing nodes, such as Call SessionControl Functions (CSCF), or application feature servers in 3GPP IMScore network or 3GPP LTE networks.

Various protocol interfaces, such as Diameter protocol interfaces,enable access to data in HSS from a client. Such access to data iscommonly accomplished via protocol messages, which generally are notequally critical or urgent. As an example, some Diameter queries fromI-CSCF or S-CSCF are directed to registration or re-registration ofsubscriber devices (UEs, CPEs, etc.). While initial registration iscritical for a subscriber device to receive subscribed services,re-registrations are not equally important and may remain without aresponse from HSS for a few minutes since a subscriber device typicallyrequests re-registration several minutes (for example, 10 minutes) priorto registration expiration. As another example, some message requestsfrom I-CSCF to HSS are directed to end-to-end call processing whereasother requests originated in I-CSCF are intended to an application thatissues message waiting indications.

Additionally, in complex, large (e.g., several thousand nodes) nextgeneration network deployments based on 3GPP IMS core network elementsor 3GPP LTE network elements, performance of HSS can be subjected tovarious heavy-load or overload conditions. When a HSS load is heavy, itis desirable for HSS to favor more critical application requests ratherthan non-critical ones. Moreover, when a HSS is in an overloadcondition, the HSS can reject or silently drop some request messages; itis desirable for the HSS to reject or drop less critical requests first.Yet, in conventional network systems, it is common for the same clientto employ the same type of Diameter message for different serviceapplications directed to access data for different operation purposes.Accordingly, management of message requests at HSS typically fails to beefficient.

SUMMARY

The following presents a simplified summary of the subject disclosure inorder to provide a basic understanding of some aspects thereof. Thesubject summary is not an extensive overview of the disclosure and it isintended to neither identify key or critical elements of the disclosurenor delineate any scope. The sole purpose of the subject summary is topresent some concepts of the disclosure in a simplified form as aprelude to the more detailed description that is presented later.

One or more embodiments of the subject disclosure provide system(s) andmethod(s) for prioritizing protocol messages received at a server,wherein the protocol messages include an indication a client applicationthat originates the protocol messages. A client generates a requestmessage and incorporates a data unit in the request message, the dataunit indicates type of service application that triggers generation ofthe request message. The client conveys the request message to a serverin a centralized network repository, wherein the server is configured torespond to the request message. To supply data in response to themessage request, the server prioritizes the request message based atleast on the data unit that conveys the type of service application. Theserver can assign a set of request messages to a group of schedulingqueues based at least on ranking of the type of service associated withat least one request message in the set of request messages. In thealternative or in addition, the server can assesses performancecondition and can reject one or more request messages based at least ona ranking of the type of service associated with the one or more requestmessages.

Aspects, features, or advantages of the subject disclosure can beexploited in most any or any packet-based core network that relies atleast on a request-reply messaging exchange with a network repository toaccess data related to providing packet-based service(s) to a subscriberdevice. The packet-based core network can be part of a wireline orwireless communication network.

To the accomplishment of the foregoing and related ends, the disclosure,then, comprises the features hereinafter fully described. The followingdescription and the annexed drawings set forth in detail certainillustrative aspects of the disclosure. However, these aspects areindicative of but a few of the various ways in which the principles ofthe subject disclosure may be employed. Other aspects, advantages andnovel features of the subject disclosure will become apparent from thefollowing detailed description when considered in conjunction with thedrawings.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic example network system that can operate inaccordance with aspects described herein.

FIG. 2 represents an example client-server system that can enable andexploit prioritization of protocol message requests in accordance withaspects described herein.

FIG. 3 illustrates an example embodiment a component that generatesprotocol message(s) in in accordance with aspects described herein.

FIG. 4 represents an example Diameter protocol message in accordancewith aspects of the subject disclosure.

FIG. 5 displays an example set of attribute values for attributed name“App Type” applicable to AVPs in respective Diameter request messagesaccording to aspects described herein.

FIG. 6 presents an example method for issuing a request message withinan authorization, authentication, and accounting (AAA) protocol in acommunication network according to aspects described herein.

FIG. 7 presents an example method for generating a request message foran AAA protocol according to aspects described herein.

FIG. 8 displays an example method for managing a request message withinan access protocol transaction according to aspects described herein.

FIG. 9 illustrates an example method for prioritizing a request messagewithin an access protocol according to aspects described herein.

FIG. 10 presents an example computing environment in which the variousaspects of the specification can be implemented.

FIG. 11 presents a schematic block diagram of an example computingenvironment in accordance with aspects described herein.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject innovation. It may be evident, however,that the subject innovation may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectinnovation.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “node,” “selector,” “interface,” and the like areintended to refer to a computer-related entity or an entity related toan operational apparatus with one or more specific functionalities,wherein the entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a server or network controller, and the server or network controllercan be a component. One or more components may reside within a processand/or thread of execution and a component may be localized on onecomputer and/or distributed between two or more computers. Also, thesecomponents can execute from various computer readable media havingvarious data structures stored thereon. The components may communicatevia local and/or remote processes such as in accordance with a signalhaving one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network such as the Internet with other systemsvia the signal). As another example, a component can be an apparatuswith specific functionality provided by mechanical parts operated byelectric or electronic circuitry, which is operated by a software, orfirmware application executed by a processor, wherein the processor canbe internal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components. As further yet another example, interface(s) caninclude input/output (I/O) components as well as associated processor,application, or Application Programming Interface (API) components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Furthermore, in the subject disclosure, the term “set” is intended torefer to groups of one or more entities; for example, a set of datapackets refers to one or more data packets. However, as employed herein,the term “subset” can include the empty set unless otherwise noted, asin cases in which, for instance, disclosure of a subset of one or moreentities is intended to expressly avoid the empty subset.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth.

With reference to the drawings, FIG. 1 is a schematic example networksystem 100 that can operate in accordance with aspects described herein.A packet-based core network 110 provides a variety of services to asubscriber. The services include numerous packet-based services (e.g.,IP-based services) comprising VoIP, video exchange, digital musicexchange, digital photograph exchange, IP Television (IPTV) clips, ormost any or any packetized digital content. In one or more embodiments,packet-based core network 110 is a 3GPP IMS core network. Service can beprovided at least in part via a protocol for session establishment, suchas session initiation protocol (SIP) or the H.323 suite of signalingprotocols. Packet-based core network 110 includes a control layer 114that enables session establishment control and routing functionality forservice sessions. Sessions primarily include data sessions; for example,VoIP call sessions. Control layer 114 can receive signaling that conveysa request to establish a session (call session, data session, etc.) and,in response to such request, routes the session to one or moreapplication servers (e.g., application server(s) 126). Control layer 114includes one or more session control node(s) 118. In example networksystem 100, the one or more application servers (ASs) are part of a setof application servers that are deployed within an application layer122. The one or more ASs can include SIP AS(s), IP Multimedia ServiceSwitching Function (IM-SSF) server(s), Customized Applications forMobile Networks Enhanced Logic (CAMEL) server(s), or OSA ServiceCapability Server(s). In addition, as illustrated, packet-based corenetwork 110 includes gateway nodes 130, comprising circuit-switched (CS)gateway node(s) 134 and packet-switched (PS) gateway node(s) 138; forexample, embodiments in which packet-based core network 110 is a 3GPPIMS core network, CS gateway node(s) 134 can include , Signaling Gatewaynode(s) (SWG) and PS gateway node(s) can include Media Gateway (MGW)node(s).

As part of the providing a service to a subscriber device (a mobiledevice, a customer premises equipment, etc.), packet-based core network110 can acquire (e.g., extract, receive) data from a centralized networkrepository 150. Data acquired from the centralized network repositorycan be utilized by packet-based core network 110 to allocate networkresources to a subscriber device. The centralized network repository 150includes one or more server(s) 154 and a centralized data storagefunctionally coupled to the one or more server(s) 154. The centralizeddata storage 158 comprises subscriber data (subscriber profiles,subscriber credentials, etc.). In an aspect, centralized data storage158 operates as a central logical unit, even though can begeographically distributed. In addition, centralized data storage 158affords various redundancy mechanisms for data integrity, such asstorage pairs. In embodiments in which packet-based core network 110 isa 3GPP IMS core network or a 3GPP LTE network, the centralized networkrepository 150 is a Home Subscriber Server; in such embodiments, the HSScan be a complex, large system with multiple servers (e.g., server(s)154) deployed in multiple functional layers comprising a variety ofmodules that provide functionality to the HSS.

Acquisition of data from centralized network repository 150 can beenabled, at least in part, through interface(s) 145. Interface(s) 145can include components that enable exchange of data and signalingamongst the packet-based core network 110 and the centralized networkrepository 150 in accordance with various access protocols (Kerberosprotocol, Remote Authentication Dian In User Service (RADIUS) protocol,Terminal Access Controller Access-Control System Plus (TACACS+)protocol, Diameter protocol, Lightweight Directory Access Protocol(LDAP), etc.) and related transport protocols (Transmission ControlProtocol (TCP), Stream Control Transmission Protocol (SCTP), etc.).Features of exchange of data and signaling can be specific to thenetwork element, or network node, in packet-based core network (CN) 110that communicates with centralized network repository 150, and one ormore servers therein; such features can be provided through execution ofone or more procedures in the network element. Accordingly, interface(s)145 can enable, at least in part, a plurality of interfaces such as Cx,Sh, Si, Dx, Dh, S6a, or the like. Interface(s) 145 Interface(s) 145 canbe embodied in at least one of conventional link(s) (e.g., a fiber opticlink, an Ethernet link, a T1/E1 line, wireless link(s) . . . ),reference link(s) (e.g., Gi, Gn . . . ), or one or more components of anaccess network (not shown), which can be wireline or wireless andprivate, semiprivate or public.

A network element in packet-based core network 110 can be a clientcomponent, or client, of the centralized network repository 150 if anaccess protocol interface is available to the network element. For anetwork element that includes at least one procedure (e.g., a set ofcomputer-executable instructions) and at least one component configuredto execute the at least one procedure, the access protocol interface isavailable. As an example, in an embodiment in which packet-based CN 110is a 3GPP IMS core network and centralized network repository is a HSS,a network element can be a HSS client if a Diameter protocol interfaceis available to the network element—S-CSCF nodes, I-CSCF nodes, P-CSCFnodes, application servers are HSS clients. Accordingly, exchange ofdata and signaling amongst such network element and a server in the setof servers 154 (represented as server(s) 154) can occur in accordancewith various client-server modalities. In an aspect, at least one clientin the set of servers 154 can receive a plurality of protocol messagesfrom a client and, in response, the at least one server can supply oneor more protocol messages. Aspects or features of the subject disclosurecan be implemented in front-end servers, and scheduling modules therein,that interface with HSS clients directly. Various features or aspects ofexchange of protocol messages amongst a client in packet-based corenetwork 110 and a server in centralized network repository 150 aredescribed next.

FIG. 2 represents an example client-server system 200 that can enableand exploit prioritization of protocol message requests in accordancewith aspects described herein. The subject example system includes aclient component 210 and a server 250; in the subject specification andannexed drawings client component 210 is also referred to as client 210.In an aspect, client 210 can be a session control node (e.g., S-CSCF,I-CSCF, P-CSCF, or Breakout Gateway Control Function (BGCF)) withincontrol layer 114 or an application server in application layer 122. Inaddition, client 210 can be a network access server (NAS) or a gatewaynode that is part of gateway nodes 130. Client 210 is functionallycoupled (e.g., communicatively coupled) to server 250, which can be aserver in the set of servers 154; as described supra, server 250 canenable management of data in a centralized storage layer (e.g., 158). Inan aspect, such management can include collection of data, delivery ofdata, compression and restoration of data, reception and transmission ofsignaling, or the like. Interface 245 enables, at least in part,exchange of data and signaling amongst client 210 and server 250 inaccordance with a communication protocol (e.g., TCP, SCTP). In addition,as indicated hereinbefore, the data and signaling that are exchanged canbe specific to an access protocol, e.g., a protocol that accomplish aspecific response to a request for access to network resourcesassociated with client 210 and server 250—the access protocol can be anetwork attachment protocol, an authentication protocol, or anauthentication, authorization, and accounting (AAA) protocol.

In the illustrated embodiment, the client component 210 includes arequest source component 214 that can initiate a message associated withthe access control protocol (e.g., Kerberos protocol, Diameter protocol,LDAP) in response to a request for service (not shown) received at theclient component 210. In an aspect, the message can be a request messagethat is specific to the access control protocol (network attachmentprotocol, AAA protocol, etc.); for example, the request message can be aDiameter request message, such as Location-Info-Request (LIR),Multimedia-Authorization-Request (MAR), Server-Assignment-Request (SAR),or the like. A request message can include a data unit that conveys atype of service provided by the client 210 and the elicited generationof the request message. The data unit can be an attribute-value pair(AVP); however, data units other than AVPs also can be utilized. In anaspect, client 210 can exploit a set of data units retained in memory226; in the illustrated embodiment, memory 226 includes an attributestorage 228 comprising a collection 230 of sets of attributes (e.g., setof attributes 232 ₁-232 _(K), with K a positive integer) that can bespecific to a message request (LIR, MAR, SAR, etc.). At least oneattribute in at least one such set of attributes can be an AVP. Thecollection 230 is provisioned by a network operator that deploys (e.g.,installs, configures, tests, and approves) the client 210. In certainembodiments, the collection 230 may be referred to as a dictionary ofattributes and can be specific to the network operator. The networkoperator can administer (e.g., own and manage or lease and manage) apacket-based core network (e.g., 3GPP IMS core network) that includesclient 210 (e.g., S-CSCF). In addition, one or more sets of attributesin the collection 230 are configurable and extensible, e.g., a set ofattributes can be augmented or reduced, and can be specific tocharacteristics of the network deployed and administered by the networkoperator.

Request source component 214 generates a request message andincorporates a data unit (e.g., attribute-value pair) that characterizesthe type of service that originated the request message; the attributeis one of the attributes in collection 230. In contrast to conventionalsystems, request source component 214 produces a request message thatallows server 250 to distinguish amongst the same type of messagerequests issued by client 210. As an illustration, it should beappreciated that in a conventional (e.g., standardized) system (e.g.,HSS in a 3GPP network), a S-CSCF node employs the same MAR and SARmessages for initial registration and re-registration processing, whileI-CSCF uses the same LIR message for call processing and notificationfor message waiting in some implementation. In the subject disclosure,such messages can be readily distinguished trough the data unit that canincorporated in such messages.

In certain embodiments, e.g., example embodiment 300 illustrated in FIG.3, request source component 214 includes a request composition component304 that generates the request message and identifies the serviceapplication (or client application) that triggers the request message;for instance, client 210 can be an I-CSCF node and the serviceapplication can be Call Processing. In an aspect, request componentcomponent 304 selects an attribute name as part of an AVP intended tocharacterize the type of service that originated the message request. Inan aspect, the attribute name can be “App Type”, even though other namescan be employed. In addition, request composition component 304 conveyssuch identification to attribute manager component 308, also referred toas attribute manager 308 in the subject disclosure. In response, andbased at least on the identification of the service application, theattribute manager 308 extracts an attribute value from attribute storage228, and supplies the attribute value to request composition component304. Request composition component 304 incorporates the attribute valuein the AVP intended to characterize the type of service and generates amessage request, which can be a Diameter protocol request message, suchas LIR, MAR, SAR.

To elicit generation of the request message (e.g., Diameter requestmessage), client 210 can execute one or more procedures that embody aservice application, also referred to as service. As an example, theservice application can be an application that allows InitialRegistration of a device, mobile or otherwise, or an application thatallows Re-registration of the device. As another example, the requestfor service (not shown) can be a request for end-to-end sessionprocessing. As yet another example, the request for service (not shown)can be a request to issue (e.g., generate and deliver) a message waitingindication. In conventional systems (e.g., 3GPP IMS core network andHSS) a client can issue a single Diameter message request for aplurality of disparate service applications, wherein the client deliversthe single Diameter message request to a server in a centralized networkrepository. In contrast, example client-server system 200 issues requestmessage(s) that can convey a type of service via the data unit thatdiscloses the type of service that provokes generation of the requestmessage, and thus allows server 250 to distinguish request messages ofthe same type yet elicited in response to execution of disparate serviceapplications.

The request source component 214 can convey the request message tointerface component 218, which can deliver the request message to server250. It should be appreciated that interface component 218 also candeliver reply or answer messages. Interface component 218 can beparticular to client 210 and can execute a group of procedures (e.g., asoftware application or a firmware application) to implement a specificinterface that allows exchange (e.g., delivery and reception) of dataand signaling with server 250. The group of procedures can be retainedin interface code 238, also referred to as interface 238, as part ofprotocol storage 236 in memory 226; code in interface 238 iscomputer-executable code. As an example, in embodiments in which client210 is an application server, interface component 218 can implement, atleast in part, a Sh interface. As another example, in embodiments inwhich client 210 is a S-CSCF node, interface component 218 canimplement, at least in part, a Cx interface. As yet another example,interface component 218 can implement a Si interface in case client 210is embodied in IM-SSF node.

In the illustrated example embodiment, client 210 includes one or moreprocessor(s) 222 configured to provide, or that provide, at least partof the described functionality of request source component 214 andinterface component 218. The one or more processor(s) 222 can executecomputer-executable code instructions (not shown in FIG. 2) stored inmemory 226 to provide the described functionality of client 210. Suchcomputer-executable code instructions can include program modules orsoftware application(s) or firmware application(s) that implement, forexample, several of the methods described in the subject disclosure andassociated, at least in part, with functionality of client 210. Itshould be appreciated that each of the one or more processor(s) 222 canbe a centralized element or a distributed element. In distributedscenarios, the one or more processor(s) 222 can be part of the variouscomponents that comprise client 210. Memory 226 also stores data, suchas data structures, data objects, metadata, numerical variables andparameters, logical variables, or the like. In addition, processor(s)222, memory 226, and the various components within client 210 canexchange data and signaling via bus 225. In an aspect, bus 225 can beembodied in one or more of a system bus, an address bus, a message bus,a memory bus, a power bus in accordance with various hardware, firmware,or software implementations.

With respect to server 250, interface component 258 can receive protocolmessages from client 210. To receive such messages, interface component258 can execute a group of procedures (e.g., a software application or afirmware application) that implement an interface that enables exchangeof data and signaling with client 210; the interface is specific to theclient 210, e.g., Sx, Sh, Si, or the like. The group of procedures canbe retained in interface code 270, also referred to as interface 270, aspart of protocol storage 268 in memory 266; code in interface 270 iscomputer-executable code. In an aspect, interface component 258 receivesa request message that includes an indication of the type of servicethat triggered the request message, as described supra. The interfacecomponent 258 can supply the request message to scheduler component 254,which exploits such indication of the type of service to prioritize agroup of one or more request messages in accordance with a schedulingpolicy. As illustrated, the scheduling policy can be retained inscheduling policy storage 272 within memory 266.

The scheduling policy (not shown) can be based at least on an indicationof type of service. In addition, the scheduling policy also can be basedon at least on a class-of-service (COS) prioritization scheme. Moreover,the scheduling policy also can exploit one or more overload protectionmechanisms. In addition, the scheduling policy (not shown) can bespecific to architecture (e.g., software application(s) or hardwarecomponent(s)) of server 250. In an embodiment, server 250 can supportmultiple scheduling queues for incoming tasks. In such embodiment, andbased in part on the indication of type of service (e.g., “App Type”attribute and related value), the scheduling policy (not shown) canenable scheduler component 254, for example, to rank and assign incomingmessage requests to different scheduling queues based at least in parton priority of a type of service provided by client 210. Priority of thetype of service can be established by one or more operational criteria.In an additional or alternative embodiment, the scheduling policy (notshown) based at least on the indication of type of service (e.g., “AppType” information) can be part of an overload protection mechanism(s)(method(s), component(s), or combination thereof) available to server250. The overload protection mechanism(s) mitigate overload condition(s)or remediate (e.g., recover from) overload condition(s). Values adoptedby a group of key performance indicators (KPIs) of the server 250 canreveal overload or non-overload condition—if at least one KPI in suchgroup is above a predetermined thresholds, an overload condition isreached. Severity of the overload condition can be dictated by thenumber of KPIs that are above threshold. The group of KPIs can include anumber of active processes or threads (e.g., processor load); a numberof current or nearly current request messages; virtual memory usage,physical memory used. In situation (s) in which the server 250 is inoverload condition, such scheduling policy (not shown) can enable server250 to select one or more request messages to be rejected or dropped.

In the illustrated example embodiment, server 250 includes one or moreprocessor(s) 262 configured to provide, or that provide, at least partof the described functionality of scheduler component 254 and interfacecomponent 258. The one or more processor(s) 262 can executecomputer-executable code instructions (not shown in FIG. 2) stored inmemory 266 to provide the described functionality of server 250. Suchcomputer-executable code instructions can include program modules orsoftware application(s) or firmware application(s) that implement, forexample, various of the methods described in the subject disclosure andassociated, at least in part, with functionality of server 250. Itshould be appreciated that each of the one or more processor(s) 262 canbe a centralized element or a distributed element. In distributedscenarios, the one or more processor(s) 262 can be part of the variouscomponents that comprise server 250. Memory 266 also stores data, suchas data structures, data objects, metadata, numerical variables andparameters, logical variables, or the like. In addition, processor(s)262, memory 266, and the various components within server 250 canexchange data and signaling via bus 265. In an aspect, bus 265 can beembodied in one or more of a system bus, an address bus, a message bus,a memory bus, a power bus in accordance with various hardware, firmware,or software implementations.

FIG. 4 presents a diagram 400 of example Diameter protocol message 420that enables issuance of a Diameter message request in accordance withaspects of the subject disclosure. Even though a message for Diameterprotocol is illustrated, attribute name and related attribute valuesdisclosed herein can be utilized to expand protocol messages I in otheraccess protocols, such as Kerberos, RADIUS, TACACS+, or the like.Example diameter protocol message 420 includes a specificattribute-value pair (AVP) that is unavailable in conventional systems;such specific AVP enables a server that manages data in a centralizednetwork repository (e.g., 110) to prioritize a Diameter request messagebased in part on a type of client (e.g., session control nodes,application servers, or network access servers) that triggers theDiameter request message.

Example Diameter protocol message 420 includes a Version field 424 of 1octet (8 bits); scale 410 represents a span of 32 bits. For example, theVersion field 424 can be set to 1 (e.g., 00000001) to indicate DiameterVersion 1. To disclose the length of the Diameter message including theheader fields a Message Length field 428, comprising three octets, isalso included in the example Diameter protocol message 420. In addition,a 1-octet field represents a Command Flags field 432. Each bit in theCommand Flags field 432 can be assigned as follows: If bit 0 is set to“R”, then the example Diameter protocol message 420 is a requestmessage; if bit 1 is set to “P”, then the example Diameter protocolmessage 420 may be proxied, relayed, or redirected; if bit 2 is set to“E”, then the example Diameter protocol message 420 contains a protocolerror and is referred to as “error message”—such bit 2 is not configuredin a request message (bit 1 set to R); if bit 3 is set to “T”, then theexample Diameter protocol message 420 is a potentially re-transmittedmessage. Bits 4-7 in the Command Flags field 432 are commonly reserved(“r”) for customized utilization of the example Diameter protocolmessage 420.

The example Diameter protocol message 420 also includes a Command Codefield 436, which spans three octets and conveys a command associatedwith the example Diameter protocol message 420. Furthermore, afour-octet Application Identifier (ID) field 440 is included to specifyan application to which the example Diameter message 400 applies; theapplication can be an authentication application, an accountingapplication, or a vendor-specific application. Application ID field 440can adopt a value within a first range of hexadecimal numbersestablished by Internet Assigned Numbers Authority (IANA) forstandardized applications, or a value within a second range ofhexadecimal numbers determined by IANA for vendor-specific applications,or services. A vendor-specific value can be assigned a “SMI NetworkManagement Private Enterprise Codes” value encoded in network byteorder. Further yet, a four-octet Hop-by-Hop Identifier field 444 and afour-octet End-to-End Identifier field 448 can be included to enable,respectively, matching requests and replies, and detecting duplicatemessages.

Additionally, example Diameter protocol message 420 includes a set of32-bit Attribute Value Pair (AVP) fields—such set is labeled withnumeral 452 and referred to herein as set of AVPs 452. Such AVPsencapsulate information relevant to the example Diameter message 420. Inan aspect of the subject disclosure, an AVP field 456 that discloses atype of application, or service, that elicits generation of the exampleDiameter protocol message is added in the set of AVPs 452—AVP field 456can be incorporated in response to setting bit 1=R in the Command Flagfield 432. As indicated supra, the subject AVP field is unavailable inconventional Diameter protocol messages.

As an illustration, AVP field 456 can be formed by an attribute name“App Type” and an attribute value (Att_value) characteristic of theclient application, or client service, that triggers a request message.In an aspect, various attribute values can be defined for variousrequest messages—diagram 500 in FIG. 5 presents an example set ofattribute values for attributed name “App Type” applicable to respectiveDiameter request messages. As described supra, the AVP fields determinedby (“App Type”, Att_value) can be employed in AAA protocol(s) other thanDiameter protocol. In addition, such AVP fields can be utilized in oneor more authentication protocols (e.g., Kerberos protocol). Asillustrated in diagram 500, and based on attribute values of “App Type”,Diameter request messages Multimedia-Auth-Request (MAR; CommandCode=303) and Server-Assignment-Request (SAR; Command Code=301) whentriggered in response to execution of an “Initial Registration”application can be distinguished from MAR and SAR requests triggered inresponse to execution of a “Re-Registration” application. A messagerequest elicited by execution of Initial Registration applicationincludes an “INI_REG” value for “App Type”, whereas a request messageoriginated from execution of Re-Registration can include a “RE_REG”value for “App Type”. Similarly, Diameter message requestUser-Authorization-Request (UAR) triggered by Initial Registration canbe distinguished from UAR triggered by Re-Registration. Additionally oralternatively, Diameter message request Location-Info-Request (LIR) canbe distinguished through disparate assignment of Att_value: (i) For LIRmessage in response to Call Processing service, Att_value can adopt thevalue “CALL”; (ii) for LIR message in response to Message Waiting Notifyservice, Att_value can adopt the value “MWI”; (iii) for LIR message inresponse to Presence Service application, Att_value can equate“PRESENCE”; and (iv) for LIR message that results from execution ofShort Messaging service, Att_value can be “SMS”.

At least one advantage emerges from the various aspects of the subjectdisclosure: A group of request messages of the same type (e.g., LIR) canbe distinguished in accordance with type of service that originates eachrequest message (e.g., LIR) in the group of request messages. As anexample, the subject disclosure enables distinction amongst a LIRmessage originated from Message Waiting Notify service from another LIRmessage originated in Call Processing service. As another example, thesubject disclosure also enables distinction amongst a MAR message due toInitial Registration service from a MAR message due to Re-registrationservice. Thus, as a result of such distinction, the group of requestmessages can be prioritized based at least on criticality of the servicethat elicits a message request. Accordingly, operation of a server in acentralized network repository (e.g., HSS in a 3GPP network) can be moreefficient than in conventional systems, particularly, though notexclusively, in heavy-load or overload performance condition. Moreover,based at least on such distinction, scheduling disciplines and relatedscheduling policies can be enhanced through introduction offunctionality that allows favoring critical message requests overnon-critical message requests. It should be appreciated that inconventional systems, such distinction amongst a group of requestmessages of the same type is unavailable. Therefore, in conventionalsystems, scheduling policies typically prioritize according to requestmessage type; type of interface associated with transport of a requestmessage; type of network node, or call processor; yet, schedulingpolicies in conventional systems do not differentiate amongst type ofclient application, or service application, that originates a requestmessage.

Various aspects of the subject disclosure can be automated throughartificial intelligence (AI) methods to infer (e.g., reason and draw aconclusion based on a set of metrics, arguments, or known outcomes incontrolled scenarios), for example, priority rankings for disparate AVPsthat can be conveyed in a message request. Artificial intelligencetechniques typically apply advanced mathematical algorithms—e.g.,decision trees, neural networks, regression analysis, principalcomponent analysis (PCA) for feature and pattern extraction, clusteranalysis, genetic algorithm, or reinforced learning—to a data set; e.g.,the collected subscriber intelligence in the case of subscribersegmentation. In particular, one of numerous methodologies can beemployed for learning from data and then drawing inferences from themodels so constructed. For example, Hidden Markov Models (HMMs) andrelated prototypical dependency models can be employed. Generalprobabilistic graphical models, such as Dempster-Shafer networks andBayesian networks like those created by structure search using aBayesian model score or approximation also can be utilized. In addition,linear classifiers, such as support vector machines (SVMs), non-linearclassifiers like methods referred to as “neural network” methodologies,fuzzy logic methodologies also can be employed.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIGS. 6-9. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein canalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methodologies.Furthermore, not all illustrated acts may be required to implement adescribed example method in accordance with the subject specification.Further yet, two or more of the disclosed methods can be implemented(executed, performed, etc.) in combination with each other, toaccomplish one or more features or advantages described herein.

Method(s) disclosed throughout the subject specification and annexeddrawings are capable of being stored on an article of manufacture tofacilitate transporting and transferring such method(s) to computers orchipsets with processing capability(ies) for execution, and thusimplementation, by a processor, or for storage in a memory. In anaspect, one or more processors that enact method(s) described herein canbe employed to execute computer-executable code instructions retained ina memory, or any computer-readable or machine-readable medium, toimplement method(s) described herein; the code instructions, whenexecuted by the one or more processor implement or carry out the variousacts in the method(s) described herein. The computer-executable codeinstructions, also referred to herein as code instructions, provide acomputer-executable framework to enact, or implement, the method(s)described herein.

FIG. 6 presents a flowchart of an example method 600 for issuing arequest message within an access protocol (e.g., authorization,authentication, and accounting (AAA) protocol) in a communicationnetwork according to aspects described herein. A client within apacket-based core network can implement (e.g., execute, instruct toexecute, etc.). In an embodiment, as described supra, the packet-basednetwork can be an IMS core network and the client can be a S-CSCF node,an I-CSCF node, or an application server. At act 610, a request messagethat includes an indication of type of service is generated. The clientprovides the service by executing an application and, in response toexecution, the service elicits the request message. The request messageis specific to the access protocol (e.g., AAA protocol) and theindication is a data unit or field attribute formatted in accordancewith the access protocol (e.g., AAA protocol). In one or moreembodiments, the AAA protocol is Diameter protocol and the requestmessage is Diameter message with a command field octet set to “Request”;the data unit that embodies the indication is an attribute-value pair(AVP). In an aspect, the AVP can be identified generically as“Application Type” or “App Type” and assigned a representation code forinsertion in a header of the AVP; as described supra, an “App Type” AVPhas a specific attribute name related to the service (see, e.g., FIG.5). At act 620, the request message is delivered to at least one serverin a centralized network repository. In an aspect, the server is part ofa data management layer and administers data (data structures, dataobjects, metadata, numerical variables and parameters, logicalvariables, etc.) in a centralized network repository layer.

FIG. 7 presents a flowchart of an example method 700 for generating arequest message according to aspects described herein. The subjectexample method can be part of act 610, and can be implemented (e.g.,executed) by one or more components that implement example method 600.The subject example method also can be enacted by one or more processorsfunctionally coupled to the one or more components, and that executecomputer-readable code instructions retained in one or more memory(ies)to provide at least part of the functionality of the one or more networkcomponents. At act 710, a request message is initiated in response to arequest for service. A client associated with the request for servicecan trigger, in part, the request message. Initiating the requestmessage can include identifying such client and determining a set offield attributes related to the request message. The request for servicecan be in control plane (e.g., registration or re-registration of adevice, mobile or otherwise) of the packet-based core network or in userplane (e.g., call session establishment request) of the packet-basedcore network. As discussed supra, the request message is specific to theaccess protocol (e.g., AAA protocol) and the indication is a data unitor field attribute formatted in accordance with the accessprotocol—e.g., Diameter protocol, RADIUS protocol, TACACS+ protocol,Kerberos protocol, or the like.

At act 720, a data unit is acquired (extracted, received, etc.) inresponse to initiating the request message; the data unit characterizesa type of service related to the service that triggered initiating therequest message. In an aspect, the data unit can be retained in memorystorage (e.g., a register, a database, a file . . . ) that is local tothe client, or one or more components therein, that implement thesubject example method. As described supra, the data unit can beformatted in accordance with the access protocol protocol. In a scenarioin which the access protocol (e.g., AAA protocol) is Diameter protocol,the data unit can be an attribute-value pair (AVP); for example, thedata unit can be an AVP that includes an attribute name, such as“Application Type” or “App Type”, and a related attribute value, adescribed hereinbefore (see, e.g., FIG. 5). At act 730, the data unit isincorporated in the request message. As an example, for Diameterprotocol, incorporating the data unit includes embedding it in the AVPportion of a Diameter message; the data unit can be a composite ofvarious data that are introduced in the header of the Diameter messageand as part of the payload data.

FIG. 8 presents a flowchart of an example method 800 for managing arequest message within an access protocol (e.g., AAA protocol)transaction according to aspects described herein. Such transaction canbe part of providing service(s) in a communication network, wireless orotherwise. A server within the communication network can implement(e.g., execute, instruct to execute, etc.); the server can be part of acentralized network repository that is functionally (e.g.,communicatively) coupled to a packet-based CN. In an embodiment, asdescribed supra, the packet-based CN can be an IMS core network and theserver can be a node (or a network element) within the Home SubscriberServer (HSS). At act 810, a request message is received, wherein therequest message includes an indication of type of service. As describedsupra, the type of service is related to a service that triggers therequest message. At act 820, the request message is scheduled based atleast on the indication of the type of service. The server thatimplements the subject example method can exploit various schedulingdisciplines in combination with the indication in order to prioritizethe request message. As described supra, such prioritization can dependat least in part on architecture (software architecture, hardwarearchitecture, or both) of the centralized network repository. In ascenario in which the architecture of the centralized network repository(e.g., HSS in 3GPP network) allows multiple scheduling queues forincoming tasks, a task scheduling policy based on the indication (e.g.,an “App Type” AVP) can enable, at least in part, assigning or sorting aset of incoming request messages to a group of scheduling queues basedat least on priority of each service type (or application type).Alternative or additional prioritization can be effected, such as thatillustrated in FIG. 9.

Example method 900 illustrates a method for scheduling a messagerequest; the subject example method is suitable for complementing orsupplementing overload protection algorithm(s) employed by a server thatreceives the message request and that supplies a response, such asDiameter answer message. At act 910, a request message is received,wherein the request message includes an indication of service type thatcharacterizes a service that elicited the request message. At act 920, aperformance condition of at least one server configured to respond tothe request message is assessed. Responding to the request message caninclude generating and delivering an answer message (e.g., a Diameteranswer message). At act 930, it is determined if a performance conditionis an overload condition. Determination can be based at least one acomparison of a group of KPIs of the at least one server with a group ofrespective predetermined thresholds; as described supra, the group ofKPIs comprising a number of active processes or threads (e.g., processorload); a number of current or nearly current request messages; virtualmemory usage, physical memory used. In the affirmative case, a priorityis assigned to the request message based at least on a scheduling policythat ranks the service type at act 940. At act 950, the request messageis scheduled based at least on the priority and a first schedulingdiscipline. In a scenario in which the performance condition isnon-overload condition, at act 960, the request message is scheduledbased on at least a second scheduling discipline under non-overloadcondition.

In order to provide additional context for various aspects of thesubject specification, FIG. 10 and the following discussion are intendedto provide a brief, general description of a suitable computingenvironment 1000 in which the various aspects of the specification canbe implemented. While the specification has been described above in thegeneral context of computer-executable instructions that may run on oneor more computers, those skilled in the art will recognize that thespecification also can be implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the specification may also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer-readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disk (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

With reference again to FIG. 10, the example environment 1000 forimplementing various aspects of the specification includes a computer1002, the computer 1002 including a processing unit 1004, a systemmemory 1006 and a system bus 1008. The system bus 1008 couples systemcomponents including, but not limited to, the system memory 1006 to theprocessing unit 1004. The processing unit 1004 can be any of variouscommercially available processors. Dual microprocessors and othermulti-processor architectures may also be employed as the processingunit 1004.

The system bus 1008 can be any of several types of bus structure thatmay further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1006includes read-only memory (ROM) 1010 and random access memory (RAM)1012. A basic input/output system (BIOS) is stored in a non-volatilememory 1010 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1002, such as during start-up. The RAM 1012 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1002 further includes an internal hard disk drive (HDD)1014 (e.g., EIDE, SATA), which internal hard disk drive 1014 may also beconfigured for external use in a suitable chassis (not shown), or anexternal HDD 1015 can be present in addition to internal HDD 1014, amagnetic floppy disk drive (FDD) 1016, (e.g., to read from or write to aremovable diskette 1018) and an optical disk drive 1020, (e.g., readinga CD-ROM disk 1022 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1014, magnetic diskdrive 1016 and optical disk drive 1020 can be connected to the systembus 1008 by a hard disk drive interface 1024, a magnetic disk driveinterface 1026 and an optical drive interface 1028, respectively. Theinterface 1024 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject specification.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1002, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, may also be used in the example operating environment, andfurther, that any such media may contain computer-executableinstructions for performing the methods of the specification.

A number of program modules can be stored in the drives and RAM 1012,including an operating system 1030, one or more application programs1032, other program modules 1034 and program data 1036. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1012. It is appreciated that the specification can beimplemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1002 throughone or more wired/wireless input devices, e.g., a keyboard 1038 and apointing device, such as a mouse 1040. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1004 through an input deviceinterface 1042 that is coupled to the system bus 1008, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1044 or other type of display device is also connected to thesystem bus 1008 via an interface, such as a video adapter 1046. Inaddition to the monitor 1044, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1002 may operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1048. The remotecomputer(s) 1048 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1002, although, for purposes of brevity, only a memory/storage device1050 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1052 and/orlarger networks, e.g., a wide area network (WAN) 1054. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich may connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1002 isconnected to the local network 1052 through a wired and/or wirelesscommunication network interface or adapter 1056. The adapter 1056 mayfacilitate wired or wireless communication to the LAN 1052, which mayalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1056.

When used in a WAN networking environment, the computer 1002 can includea modem 1058, or is connected to a communications server on the WAN1054, or has other means for establishing communications over the WAN1054, such as by way of the Internet. The modem 1058, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1008 via the serial port interface 1042. In a networkedenvironment, program modules depicted relative to the computer 1002, orportions thereof, can be stored in the remote memory/storage device1050. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

The computer 1002 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE 802.11(a, b,g, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet).Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, atan 8 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example, or withproducts that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic 10BaseT wiredEthernet networks used in many offices.

FIG. 11 illustrates a schematic block diagram of an example computingenvironment 1130, in accordance with aspects described herein. Thesystem 1100 includes one or more client(s) 1110. The client(s) 1110 canbe hardware and/or software (e.g., threads, processes, computingdevices). The system 1100 also includes one or more server(s) 1120.Thus, system 1100 can correspond to a two-tier client server model or amulti-tier model (e.g., client, middle tier server, data server),amongst other models. The server(s) 1120 can also be hardware and/orsoftware (e.g., threads, processes, computing devices). The servers 1120can house threads to perform transformations by employing the subjectinnovation, for example. One possible communication between a client1110 and a server 1120 may be in the form of a data packet transmittedbetween two or more computer processes.

The system 1100 includes a communication framework 1130 that can beemployed to facilitate communications between the client(s) 1110 and theserver(s) 1120. The client(s) 1110 are operatively connected to one ormore client data store(s) 1140 that can be employed to store informationlocal to the client(s) 1110. Similarly, the server(s) 1120 areoperatively connected to one or more server data store(s) 1150 that canbe employed to store information local to the servers 1120.

It is to be noted that aspects, features, or advantages of the subjectinnovation described in the subject specification can be exploited insubstantially any wireless communication technology. For instance, 4Gtechnologies, Wi-Fi, WiMAX, Enhanced GPRS, 3GPP LTE, 3GPP2 UMB, 3GPPUMTS, HSPA, HSDPA, HSUPA, GERAN, UTRAN, LTE Advanced. Additionally,substantially all aspects of the subject innovation as disclosed in thesubject specification can be exploited in legacy telecommunicationtechnologies; e.g., GSM. In addition, mobile as well non-mobile networks(e.g., internet, data service network such as IPTV) can exploit aspector features described herein.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification and annexed drawings, terms such as“store,” “data store,” “data storage,” “database,” and substantially anyother information storage component relevant to operation andfunctionality of a component, refer to “memory components,” or entitiesembodied in a “memory” or components comprising the memory. It will beappreciated that the memory components described herein can be eithervolatile memory or nonvolatile memory, or can include both volatile andnonvolatile memory.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

Various aspects or features described herein can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. In addition, various aspects disclosed inthe subject specification can also be implemented through programmodules stored in a memory and executed by a processor, or othercombination of hardware and software, or hardware and firmware. The term“article of manufacture” as used herein is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media. For example, computer readable media can include but are notlimited to magnetic storage devices (e.g., hard disk, floppy disk,magnetic strips . . . ), optical discs (e.g., compact disc (CD), digitalversatile disc (DVD), blu-ray disc (BD) . . . ), smart cards, and flashmemory devices (e.g., card, stick, key drive . . . ).

What has been described above includes examples of systems and methodsthat provide advantages of the subject innovation. It is, of course, notpossible to describe every conceivable combination of components ormethodologies for purposes of describing the subject innovation, but oneof ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

1. A method, comprising: employing at least one processor to executecomputer-executable code instructions retained in a memory, in responseto execution by the at least one processor, the computer-executable codeinstructions perform a group of acts comprising: generating a requestmessage that includes an indication of type of service application thattriggers the request message; and delivering the request message to atleast one server in a centralized network repository.
 2. The method ofclaim 1, wherein the generating includes: initiating the request messagebased at least on a request for service associated with the serviceapplication; and in response to the initiating, acquiring the indicationof type of service application, wherein the indication is a data unitthat characterizes the type of service application.
 3. The method ofclaim 2, wherein the generating further includes: incorporating the dataunit in the request message, wherein the data unit is an attribute-valuepair and the request message is a message in an authentication,authorization and accounting (AAA) protocol.
 4. The method of claim 1,the group of acts further comprising: scheduling the request messagebased at least on the indication of type of service application thattriggers the request message.
 5. The method of claim 4, wherein thescheduling includes: assigning a set of request messages to a group ofscheduling queues based at least on priority of a type of serviceassociated with at least one request message in the set of requestmessages.
 6. The method of claim 4, wherein the scheduling includes:assessing performance condition of at least one server configured torespond to the request message; and in case the performance condition isan overload condition, assigning a priority to the request message basedat least on a scheduling policy that ranks the type of serviceassociated with the request message.
 7. A system, comprising: a requestsource component that generates a request message, wherein the requestmessage includes an indication of type of service application, theservice application triggers generation of the request message; and aninterface component that conveys the request message to a server in acentralized network repository, wherein the server is configured torespond to the request message.
 8. The system of claim 7, wherein therequest message is a message in an authentication, authorization andaccounting (AAA) protocol and the indication is a data unit specific tothe AAA protocol.
 9. The system of claim 8, wherein the AAA protocol isDiameter protocol and the data unit specific to the AAA protocol is anattribute value pair (AVP).
 10. The system of claim 7, wherein therequest source component includes a composition component that initiatesthe request message based at least on a request for service associatedwith the service application.
 11. The system of claim 10, wherein therequest component includes an a component that acquires the indicationof type of service in response to initiation of the request message. 12.The system of claim 7, wherein the server includes a schedulingcomponent that prioritizes the request message based at least on theindication of type of service application.
 13. The system of claim 12,to prioritize the request message based at least on the indication oftype of service application, the scheduling component assigns a set ofrequest messages to a group of scheduling queues based at least onranking of the type of service associated with at least one requestmessage in the set of request messages.
 14. The system of claim 12, toprioritize the request message based at least on the indication of typeof service application, the scheduling component assesses performancecondition of the server and, in case the performance condition is anoverload condition, assigns a priority to the request message based atleast on a scheduling policy that ranks the type of service associatedwith the request message.
 15. The system of claim 7, wherein the requestcomponent and the interface component are deployed within a network nodein a 3GPP IMS core network.
 16. The system of claim 15, wherein thenetwork node is one of a S-CSCF node, an I-CSCF node, or an applicationserver, and the server is included in a Home Subscriber Server.
 17. Acomputer-readable storage medium comprising computer-executable codeinstructions stored therein, wherein in response to execution by atleast one processor, the computer-executable code instructions perform agroup of acts comprising: generating a request message that includes anindication of type of service application that triggers the requestmessage; and delivering the request message to at least one server in acentralized network repository.
 18. The computer-readable storage mediumof claim 17, wherein the generating includes: initiating the requestmessage based at least on a request for service associated with theservice application; and in response to the initiating, acquiring theindication of type of service application, wherein the indication is adata unit that characterizes the type of service application.
 19. Themethod of claim 2, wherein the generating further includes:incorporating the data unit in the request message, wherein the dataunit is an attribute-value pair and the request message is a message inan authentication, authorization and accounting (AAA) protocol.
 20. Thecomputer-readable storage medium of claim 17, the group of acts furthercomprising: scheduling the request message based at least on theindication of type of service application that triggers the requestmessage, wherein the scheduling includes: assessing performancecondition of at least one server configured to respond to the requestmessage; and in case the performance condition is an overload condition,assigning a priority to the request message based at least on ascheduling policy that ranks the type of service associated with therequest message.